Add: Running SLAM in Production - A Practitioner's Guide#255
Open
Shreenabh664 wants to merge 1 commit intoRoboticsKnowledgebase:masterfrom
Open
Add: Running SLAM in Production - A Practitioner's Guide#255Shreenabh664 wants to merge 1 commit intoRoboticsKnowledgebase:masterfrom
Shreenabh664 wants to merge 1 commit intoRoboticsKnowledgebase:masterfrom
Conversation
A new article under wiki/state-estimation/ aimed at engineers about to deploy monocular SLAM. Covers (1) the SLAM algorithm landscape and why ORB-SLAM3 is the default pick for most production cases, (2) the failure modes a deployed monocular SLAM hits in the field and how to engineer for them based on a 1,760-run controlled corruption study, and (3) a smaller note on running evaluation loops locally for tuning. ~7,500 non-space chars, 3 inline figures, 5 external references with justifying blurbs.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A new article under wiki/state-estimation/ aimed at engineers about to deploy monocular SLAM. Covers:
(1) the SLAM algorithm landscape and why ORB-SLAM3 is the default pick for most production cases,
(2) the failure modes a deployed monocular SLAM hits in the field and how to engineer for them based on a 1,760-run controlled corruption study, and
(3) a smaller note on running evaluation loops locally for tuning.